About the API:
Face liveness detection helps you uncover fraud by ensuring that the image you have been provided isn’t a picture of a picture, a passport-sized image, or an image of another individual on a cell phone/laptop screen. Pair it with the Face Comparison Validator API to have complete confidence that the selfie of the individual is indeed live, and belongs to the same individual as you expect.
This API will receive the image URL that you want to check its liveness. It will provide information like face quality, if the photo is live taken, and its position in the image.
Fraud detection: Face liveness detection helps you uncover fraud by ensuring that the image you have been provided isn’t a picture of a picture, a passport-sized image, or an image of another individual on a cell phone/laptop screen.
Check image properties: Be able to detect if any image is not following your requirements. Check if the face is too far from the camera if its quality is good or poor, and avoid your users to upload images that won't be useful for your platforms.
Receive images for biometric analysis: If you are using biometric analysis in your products, is important to receive images that are taken live from your users. This API will help you with that.
Besides the number of API calls per month, there are no other limitations.
Pass the image URL that you want to check its liveness.
Receive a task ID that you will use later on the "Get Results" endpoint.
Check Liveness - Endpoint Features
Object | Description |
---|---|
Request Body |
[Required] Json |
{"Example Response":"No response example available for now."}
curl --location --request POST 'https://zylalabs.com/api/322/face+liveness+check+api/259/check+liveness' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"task_id": "123",
"group_id": "123",
"data": {
"document1": "https://i0.wp.com/post.medicalnewstoday.com/wp-content/uploads/sites/3/2020/03/GettyImages-1092658864_hero-1024x575.jpg"
}
}'
Receive the analysis from the image that you uploaded by passing its request id.
Get Results - Endpoint Features
Object | Description |
---|---|
request_id |
[Required] The request_id provided on the "Check Liveness" endpoint. |
[{"action":"check_photo_liveness","created_at":"2023-12-07T02:49:13+05:30","group_id":"123","request_id":"cbbc9300-88ba-46e2-bebe-ec024724802e","status":"in_progress","task_id":"123","type":"face"}]
curl --location --request GET 'https://zylalabs.com/api/322/face+liveness+check+api/260/get+results?request_id=d3dc6e39-a4fc-4d6d-88c8-4c23b9ddd360' --header 'Authorization: Bearer YOUR_API_KEY'
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the worldβs most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, look at the βX-Zyla-API-Calls-Monthly-Remainingβ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.
The βX-Zyla-RateLimit-Resetβ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3600, it means 3600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, itβs important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.
Service Level:
100%
Response Time:
1,410ms
Service Level:
100%
Response Time:
6,096ms
Service Level:
100%
Response Time:
2,218ms
Service Level:
100%
Response Time:
626ms
Service Level:
100%
Response Time:
987ms
Service Level:
98%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
4,800ms
Service Level:
89%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
3,942ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
224ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
8ms
Service Level:
100%
Response Time:
2,236ms